The latest updates on your projects. Learn more about Vercel for Git ↗︎

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 782600e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

Sent with 💌 from NxCloud.

I wouldn't have expected that many changes. Nice to see that this is already prepared. Thanks for the great work 💪🏼

when is that planned to be released?

Curious what the nx protocol is with new versions of insert framework here. With angular, there are a bunch of release candidates and beta builds available prior to the GA release. I would assume nx would have no problem pushing out support for version x within a day or two of the GA release. But, angular was released on November 19th and nx hasn't pushed anything angular 19 related out yet.

Is there a doc for "response time" with new releases? I fully understand each release differs in complexity given what features/changes are shipped with it. just seems between the the release candidates and beta builds there would be ample time to get something going that releases within a day or two of when the framework gets released.

They just merged and deleted the feature branch not more than 4 hours ago. I'm sure its coming soon.

I'm not pushing anyone for anything, it's a benign question :)

After migrating to 20.2.0-beta.5:

Curious what the nx protocol is with new versions of insert framework here. With angular, there are a bunch of release candidates and beta builds available prior to the GA release. I would assume nx would have no problem pushing out support for version x within a day or two of the GA release. But, angular was released on November 19th and nx hasn't pushed anything angular 19 related out yet.

Is there a doc for "response time" with new releases? I fully understand each release differs in complexity given what features/changes are shipped with it. just seems between the the release candidates and beta builds there would be ample time to get something going that releases within a day or two of when the framework gets released.

I think that the answer is in the pull request description. We are waiting for corresponding releases of NgRx and Analog right now

Can I stay on Angular 18.x with Nx 20.2.X?
I'd like to update Nx, but not Angular ATM.

Can I stay on Angular 18.x with Nx 20.2.X? I'd like to update Nx, but not Angular ATM.

Yes this should be possible as of Interactively opting out of package updates

The latest version of Nx supports the actively supported versions of Angular (current and LTS versions).

From: https://nx.dev/nx-api/angular/documents/angular-nx-version-matrix

This docs page has already been updated on master to show that the latest version of Nx supports back to Angular 17.0.0.

See: https://canary.nx.dev/nx-api/angular/documents/angular-nx-version-matrix

I think that the answer is in the pull request description. We are waiting for corresponding releases of NgRx and Analog right now

Yea, but that's this PR. I'd like to understand what the overall process is. Having NgRx hold up a release is odd... not everyone uses NgRx with Angular so it's wierd to hold a core component (angular) up because of an unrelated dependency (NgRx). Obviously, if you have NgRx in your angular app, you're not going to get too far in the upgrade path since NgRx and Angular have compatibility requirements.

I'm about a year into using Nx and like it for the most part. However, I am not a fan of an unrelated thing blocking an upgrade path of a regular app. If we migrate to a new angular version and some crazy bug was found, not only do we have to wait on Angular to push out a fix, we have to wait on Nx to push out a fix, for a fix. Understanding how they prioritize versions and decide how quick they work on it would be great information.

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.